Skip to content

Make CLI gemspec work in source containers and include executable - #3

Draft
jadenfix wants to merge 1 commit into
codex/api-persistence-20261013from
codex/ruby-cli-package-20261013
Draft

jadenfix wants to merge 1 commit into
codex/api-persistence-20261013from
codex/ruby-cli-package-20261013

Conversation

@jadenfix

Copy link
Copy Markdown
Owner

The container job fails while loading the gemspec because git is absent. Its git-file filter also excludes bin/, so installed gems lose the gemhub executable. Enumerate actual lib/bin/documentation files from the source tree and add an isolated no-Git packaging check to the existing HTTP lane.

Validation: actual Ruby3.2.3 loads the copied source-only gemspec with PATH containing noGit; verifies packaged executable and implementation. Original gemspec fails the same regression withNo suchfile git. Existing actualHTTPcreation/read/authorization/validation/duplicates/unavailable scanner/restart checkpasses. No services mocked. git diff --check clean.

FullRubyCI remains blocked by Bundler2.6.9 incompatible withRuby3.0 and malformed ESLint extends configuration; Verceldeployment remains unexplained. FullDockerimage build and gem installation/runtime dependencies not validated here. Follow-up on#2 head474d302; parentsolemerger; do not treat this boundedpackaging fix as wholeprojectcompletion.

@vercel

vercel Bot commented Oct 13, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
ruby Error Error Oct 13, 2026 1:46am UTC

Copy link
Copy Markdown
Owner Author

Independent exact-head verification — bounded packaging clear, not project/demo completion (2026-10-14)

Verified without modifying this branch.

Identity and dependency order

Independent reproduction

  1. Remote refs still resolved to the exact heads above; checkout was clean and git diff --check passed.
  2. Exact changed blobs:
    • .github/workflows/api-http.yml: c200fa02bbd51142b3e46ad2d808d19df25e8092
    • cli/gemhub.gemspec: cbc1a898197dbff9378ce11646ba1f283eb671f1
    • scripts/check_gem_package.rb: cc01ace395b3da6e00963a69754326930433605b
  3. Independent Ruby 3.3.3 WASI package build from the exact checkout:
    • loaded the gemspec from a source copy with no .git requirement;
    • built an actual gemhub-0.1.0.gem;
    • decoded the gem archive and found exactly bin/gemhub, lib/gemhub.rb, lib/gemhub/cli.rb, and lib/gemhub/version.rb;
    • confirmed the packaged version source is byte-identical to the exact checkout;
    • confirmed the checked-in executable is mode 100755;
    • result: {"ruby":"3.3.3","gem":"gemhub-0.1.0","files":["bin/gemhub","lib/gemhub.rb","lib/gemhub/cli.rb","lib/gemhub/version.rb"],"packaged_version":"0.1.0","source_executable_mode":"755"}.
  4. Hosted run 38333291521 is green on the PR merge ref with native Ruby 3.3.12:
    • syntax check: Syntax OK
    • source-only package check: PASS
    • actual loopback HTTP create/read, authorization, validation, duplicate rejection, explicit unavailable scanner, and restart persistence: PASS

Scope and remaining gates

Clear only for the bounded claim: the CLI gemspec no longer requires Git metadata and the built gem includes the executable plus implementation files.

This is not a project-completion or demo credit:

  • PR remains draft and depends on unmerged Persist gem records and verify the local Ruby API over HTTP #2.
  • The full repository CI workflow did not run for this non-main stacked base; the known Ruby 3.0/Bundler, extension lint, and container lanes remain unresolved/unverified.
  • Vercel status is failing at the exact head.
  • No source-pinned GIF or MP4 exists on this branch, so there is no media to decode or award.
  • The installed CLI runtime with all declared third-party gems, frontend/API browser integration, live providers, sandbox, benchmarks, scanner implementation, and production deployment remain unverified.
  • The gem metadata still points at the placeholder github.com/your-org/gemhub; this did not affect the bounded packaging behavior but must not be presented as release-ready metadata.

Disposition: bounded packaging verification CLEAR; merge/demo/full-project status remains blocked. Sole-merger ownership is unchanged.

This branch had an error being deployed

1 failed deployment
Preview — a05970c0 Deployed Oct 13, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant